Does TCP actually define 'TCP server' and 'TCP clients'? [closed]
Posted
by
mjn
on Stack Overflow
See other posts from Stack Overflow
or by mjn
Published on 2012-12-15T17:09:32Z
Indexed on
2012/12/16
11:06 UTC
Read the original article
Hit count: 190
In the Wikipedia article, TCP communication is explained using the terms 'client' and 'server'. It also uses the word 'peers'. But TCP actually does not define "TCP clients" and "TCP servers" - In the RFC 675 document (SPECIFICATION OF INTERNET TRANSMISSION CONTROL PROGRAM), the word "client" never appears. The RFC explains that TCP is used to connect processes over ports (sockets), and that 'A pair of sockets form a CONNECTION which can be used to carry data in either direction [i.e. full duplex].
Calling the originating party the "client" seems to be common practice. But this client/server communication model is not always applicable to TCP communication. For example take peer-to-peer networks. Calling all processes which open a socket (and wait for incoming connections from peers) "TCP servers", sounds wrong to me. I would not call my uncle's telephone device a "Telephony server" if I dial his phone number and he picks up.
© Stack Overflow or respective owner